Dec 02 02:03:16.195 INFO testing Yatekii/rust_playground against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 02 02:03:16.195 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:03:16.764 INFO [stdout] 6f859b9214d0968ec63e3ff26eb8ff7f984d88fa092d3b119243142df781412c
Dec 02 02:03:16.766 INFO running `"docker" "start" "-a" "6f859b9214d0968ec63e3ff26eb8ff7f984d88fa092d3b119243142df781412c"`
Dec 02 02:03:18.329 INFO [stderr] usermod: no changes
Dec 02 02:03:18.395 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 02:03:18.395 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 02:03:18.395 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:03:18.395 INFO [stderr] files will be included as a benchmark target:
Dec 02 02:03:18.395 INFO [stderr] 
Dec 02 02:03:18.395 INFO [stderr] * /source/benches/cell.rs
Dec 02 02:03:18.395 INFO [stderr] 
Dec 02 02:03:18.395 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:03:18.395 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 02:03:18.395 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 02:03:18.395 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:03:18.395 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:03:18.395 INFO [stderr] 
Dec 02 02:03:18.395 INFO [stderr] For more information on this warning you can consult
Dec 02 02:03:18.395 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:03:18.547 INFO [stderr]    Compiling elapsed v0.1.2
Dec 02 02:03:18.551 INFO [stderr]    Compiling num-complex v0.2.0
Dec 02 02:03:18.551 INFO [stderr]    Compiling approx v0.2.0
Dec 02 02:03:21.024 INFO [stderr]    Compiling alga v0.6.0
Dec 02 02:03:25.843 INFO [stderr]    Compiling nalgebra v0.15.3
Dec 02 02:03:59.635 INFO [stderr]    Compiling ncollide2d v0.16.1
Dec 02 02:04:08.891 INFO [stderr]    Compiling rust_playground v0.1.0 (/source)
Dec 02 02:04:11.300 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 52.93s
Dec 02 02:04:11.309 INFO [stderr] su: No module specific data is present
Dec 02 02:04:12.408 INFO running `"docker" "inspect" "6f859b9214d0968ec63e3ff26eb8ff7f984d88fa092d3b119243142df781412c"`
Dec 02 02:04:12.697 INFO running `"docker" "rm" "-f" "6f859b9214d0968ec63e3ff26eb8ff7f984d88fa092d3b119243142df781412c"`
Dec 02 02:04:12.963 INFO [stdout] 6f859b9214d0968ec63e3ff26eb8ff7f984d88fa092d3b119243142df781412c
Dec 02 02:04:12.969 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:04:13.493 INFO [stdout] 06869c40cd52f1ed301bc52394eeb43b1935201c91d21e33a930e9149ef0de6e
Dec 02 02:04:13.495 INFO running `"docker" "start" "-a" "06869c40cd52f1ed301bc52394eeb43b1935201c91d21e33a930e9149ef0de6e"`
Dec 02 02:04:15.370 INFO [stderr] usermod: no changes
Dec 02 02:04:15.433 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 02:04:15.433 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 02:04:15.433 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:04:15.433 INFO [stderr] files will be included as a benchmark target:
Dec 02 02:04:15.433 INFO [stderr] 
Dec 02 02:04:15.433 INFO [stderr] * /source/benches/cell.rs
Dec 02 02:04:15.433 INFO [stderr] 
Dec 02 02:04:15.433 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:04:15.433 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 02:04:15.433 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 02:04:15.433 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:04:15.433 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:04:15.433 INFO [stderr] 
Dec 02 02:04:15.433 INFO [stderr] For more information on this warning you can consult
Dec 02 02:04:15.433 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:04:15.707 INFO [stderr]    Compiling criterion-stats v0.2.3
Dec 02 02:04:15.712 INFO [stderr]    Compiling chrono v0.4.3
Dec 02 02:04:15.719 INFO [stderr]    Compiling handlebars v0.31.0
Dec 02 02:04:22.015 INFO [stderr]    Compiling simplelog v0.5.2
Dec 02 02:04:31.607 INFO [stderr]    Compiling criterion v0.2.3
Dec 02 02:04:44.466 INFO [stderr]    Compiling rust_playground v0.1.0 (/source)
Dec 02 02:04:46.235 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 30.83s
Dec 02 02:04:46.247 INFO [stderr] su: No module specific data is present
Dec 02 02:04:47.160 INFO running `"docker" "inspect" "06869c40cd52f1ed301bc52394eeb43b1935201c91d21e33a930e9149ef0de6e"`
Dec 02 02:04:47.579 INFO running `"docker" "rm" "-f" "06869c40cd52f1ed301bc52394eeb43b1935201c91d21e33a930e9149ef0de6e"`
Dec 02 02:04:47.854 INFO [stdout] 06869c40cd52f1ed301bc52394eeb43b1935201c91d21e33a930e9149ef0de6e
Dec 02 02:04:47.863 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-1/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:04:48.295 INFO [stdout] 72395ac2e1bada04bc26a5c88610b3c1a48d523e374906b16289bab207656858
Dec 02 02:04:48.300 INFO running `"docker" "start" "-a" "72395ac2e1bada04bc26a5c88610b3c1a48d523e374906b16289bab207656858"`
Dec 02 02:04:49.686 INFO [stderr] usermod: no changes
Dec 02 02:04:49.735 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 02:04:49.735 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 02:04:49.735 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:04:49.735 INFO [stderr] files will be included as a benchmark target:
Dec 02 02:04:49.735 INFO [stderr] 
Dec 02 02:04:49.735 INFO [stderr] * /source/benches/cell.rs
Dec 02 02:04:49.735 INFO [stderr] 
Dec 02 02:04:49.735 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:04:49.735 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 02:04:49.735 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 02:04:49.735 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:04:49.735 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:04:49.735 INFO [stderr] 
Dec 02 02:04:49.735 INFO [stderr] For more information on this warning you can consult
Dec 02 02:04:49.735 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:04:49.890 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.17s
Dec 02 02:04:49.913 INFO [stderr]      Running /target/debug/deps/rust_playground-e128a662e9c0be35
Dec 02 02:04:49.921 INFO [stdout] 
Dec 02 02:04:49.921 INFO [stdout] running 0 tests
Dec 02 02:04:49.921 INFO [stdout] 
Dec 02 02:04:49.921 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 02 02:04:49.921 INFO [stdout] 
Dec 02 02:04:49.943 INFO [stderr] su: No module specific data is present
Dec 02 02:04:50.708 INFO running `"docker" "inspect" "72395ac2e1bada04bc26a5c88610b3c1a48d523e374906b16289bab207656858"`
Dec 02 02:04:50.951 INFO running `"docker" "rm" "-f" "72395ac2e1bada04bc26a5c88610b3c1a48d523e374906b16289bab207656858"`
Dec 02 02:04:51.211 INFO [stdout] 72395ac2e1bada04bc26a5c88610b3c1a48d523e374906b16289bab207656858
